home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19950929-19951130
/
000382_news@columbia.edu_Tue Nov 14 14:04:16 1995.msg
< prev
next >
Wrap
Internet Message Format
|
1995-12-25
|
7KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA16657
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun>); Tue, 14 Nov 1995 09:04:24 -0500
Received: (from news@localhost) by apakabar.cc.columbia.edu (8.6.12/8.6.12) id JAA28515 for kermit.misc@watsun; Tue, 14 Nov 1995 09:04:22 -0500
Path: news.columbia.edu!watsun.cc.columbia.edu!fdc
From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: C-Kermint: Kernel Panic Sol 2.3!!
Date: 14 Nov 1995 14:04:16 GMT
Organization: Columbia University
Lines: 140
Message-Id: <48a7l0$rr0@apakabar.cc.columbia.edu>
References: <488dc7$j17@spectator.cris.com>
Nntp-Posting-Host: watsun.cc.columbia.edu
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <488dc7$j17@spectator.cris.com>,
Peter Noone <Pknoone@cris.com> wrote:
>
> I recently downloaded and compiled C-Kermit on my Sparc-5
> running Solaris 2.3 . I compiled version 5A(190) of C-kermit
> using the standard make solaris2xg with no errors. I was
> running kermit interactively and it caused a kernel panic
> that brought my machine to its knees and eventually rebooted
> in single user mode. I recovered from this incident but am
> a little wary of running kermit again.
>
> Are there any know bugs or problems that I should be aware of?
>
Plenty of them. They are documented as thoroughly as we know how in the
release note. The pertinent file is ckuker.bwr (C-Kermit for UNIX "beware"
file). I quote liberally from it below, but please note that if a user-mode
program can crash an UNIX operating system, the problem is not in the
user-mode program :-)
(3.7) C-KERMIT AND SOLARIS
C-Kermit can't be compiled successfully under Solaris 2.3 using SUNWspro cc
2.0.1 unless at least some of the following patches are applied to cc (it is
not known which one(s), if any, fix the problem):
100935-01 SparcCompiler C 2.0.1: bad code generated when addresses
of two double arguments are involved
100961-05 SPARCcompilers C 2.0.1: conditional expression with
function returning strucure gives wrong value
100974-01 SparcWorks 2.0.1: dbx jumbo patch
101424-01 SPARCworks 2.0.1 maketool SEGV's instantly on Solaris 2.3
With unpatched cc 2.0.1, the symptom is that certain modules generate
truncated object files, resulting in many unresolved references at link time.
Reportedly, "C-Kermit ... causes a SPARCstation running Solaris 2.3
to panic after the modem connects. I have tried compiling C-Kermit with Sun's
unbundled C compiler, with GCC Versions 2.4.5 and 2.5.3, with make targets
'sunos51', 'sunos51tcp', 'sunos51gcc', and even 'sys5r4', and each time it
compiles and starts up cleanly, but without fail, as soon as I dial the number
and get a 'CONNECT' message from the modem, I get:
BAD TRAP
kermit: Data fault
kernel read fault at addr=0x45c, pme=0x0
Sync Error Reg 80 <INVALID>
...
panic: Data Fault.
...
Rebooting...
The same modem works fine for UUCP/tip calling." Also (reportedly), this only
happens if the dialout port is configured as in/out via admintool. If it is
configured as out-only, no problem. This is the same dialing code that works
on hundreds of other System-V based UNIX OS's. Since it should be impossible
for a user program to crash the operating system, this problem must be chalked
up to a Solaris bug. Even if you SET CARRIER OFF, CONNECT, and dial manually
by typing ATDTnnnnnnn, the system panics as soon as the modem issues its
CONNECT message. (Clearly, when you are dialing manually, C-Kermit does not
know a thing about the CONNECT message, and so the panic is almost certainly
caused by the transition of the Carrier Detect (CD) line from off to on.)
This problem was reported by many users, all of whom say that C-Kermit worked
fine on Solaris 2.1 and 2.2. If the speculation about CD is true, then a
possible workaround might be to configure the modem to leave CD on (or off)
all the time. Perhaps by the time you read this, a patch will have been
issued for Solaris 2.3.
The following is from Karl S. Marsh, Systems & Networks Administrator,
AMBIX Systems Corp, Rochester, NY (begin quote):
"Environment:
Solaris 2.3 Patch 101318-45
C-Kermit 5A(189) (and presumably this applies to 188 and 190 also)
eeprom setting:
ttya-rts-dtr-off=false
ttya-ignore-cd=false
ttya-mode=19200,8,n,8,-
"To use C-Kermit on a bidirectional port in this environment, do not use
admintool to configure the port. Use admintool to delete any services running
on the port and then quit admintool and issue the following command:
pmadm -a -p zsmon -s ttyb -i root -fu -v 1 -m "`ttyadm -b -d /dev/term/b \
-l conttyH -m ldterm,ttcompat -s /usr/bin/login -S n`"
[NOTE: This was copied from a fax, so please check it carefully] where:
-a = Add service
-p = pmtag (zsmon)
-s = service tag (ttyb)
-i = id to be associated with service tag (root)
-fu = create utmp entry
-v = version of ttyadm
-m = port monitor-specific portion of the port monitor administrative file
entry for the service
-b = set up port for bidirectional use
-d = full path name of device
-l = which ttylabel in the /etc/ttydefs file to use
-m = a list of pushable STREAMS modules
-s = pathname of service to be invoked when connection request received
-S = software carrier detect on or off (n = off)
"This is exactly how I was able to get Kermit to work on a bi-directional
port without crashing the system." (End quote)
On the Solaris problem, also see SunSolve Bug ID 1150457 ("Using C-Kermit, get
Bad Trap on receiving prompt from remote system"). Another user reported "So,
I have communicated with the Sun tech support person that submitted this bug
report [1150457]. Apparently, this bug was fixed under one of the jumbo
kernel patches. It would seem that the fix did not live on into 101318-45, as
this is EXACTLY the error that I see when I attempt to use kermit on my
system."
Later (Aug 94)... C-Kermit dialout successfully tested on a Sun4m with a
heavily patched Solaris 2.3. The patches most likely to have been relevant:
101318-50: SunOS 5.3: Jumbo patch for kernel (includes libc, lockd)
101720-01: SunOS 5.3: ttymon - prompt not always visible on a modem connection
101815-01: SunOS 5.3: Data fault in put() NULL queue passed from
ttycommon_qfull()
101328-01: SunOS 5.3: Automation script to properly setup tty ports prior to
PCTS execution
Still later (Nov 94): another user (Bo Kullmar in Sweden) reports that after
using C-Kermit to dial out on a bidirectional port, the port might not answer
subsequent incoming calls, and says "the problem is easy enough to to fix with
the Serial Port Manager; I just delete the service and and install it again
using the graphical interface, which underneath uses commands like sacadm and
pmadm." Later Bo reports, "I have found that if I run Kermit with the
following script then it works. This script is for /dev/cua/a, -s a is the
last a in /dev/cua/a
#! /bin/sh
kermit
sleep 2
surun pmadm -e -p zsmon -s a
(end quote)
- Frank